OpenAI just shipped Codex to the ChatGPT mobile app#3008
Merged
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Appwrite has crossed the 50K GitHub stars milestone with hundreds of active contributors |
Contributor
Greptile SummaryThis PR adds a new blog post covering OpenAI's Codex mobile app launch, along with its cover image and a cache entry for the image optimizer.
Confidence Score: 5/5Safe to merge — the change is additive (new blog post, cover image, cache entry) with no impact on existing functionality. All three files are purely additive content changes. The cache entry extension matches the actual image file, the front matter fields are valid, and the product links within the body are root-relative. The only findings are cosmetic style inconsistencies that do not affect rendering or behavior. No files require special attention. Important Files Changed
Reviews (6): Last reviewed commit: "Apply suggestion from @adityaoberai" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
adityaoberai
requested changes
May 20, 2026
Comment on lines
+31
to
+39
| **Mobile access is now in preview on iOS and Android** through the ChatGPT app, across all plans including Free and Go. Before this release, Codex workflows were still primarily tied to desktop and IDE environments. | ||
|
|
||
| **Remote SSH is generally available.** The desktop app auto detects hosts from your SSH config and lets you create projects and run threads inside remote machines just like you would locally. Before this, remote environment workflows existed, but they were far less integrated and not officially streamlined inside the Codex app. | ||
|
|
||
| **Programmatic access tokens** provide scoped credentials issued directly from ChatGPT workspace settings, so Codex can be called from CI pipelines, release workflows, and internal automations without a human session. | ||
|
|
||
| **Hooks are generally available** and can be used to scan prompts for secrets, run validators, log conversations, create memories, or customize Codex behavior for specific repositories and directories. | ||
|
|
||
| **HIPAA-compliant local use** is supported for eligible ChatGPT Enterprise workspaces when Codex is used in local environments across the CLI, IDE, and App. |
Contributor
There was a problem hiding this comment.
Let's add bullets to these
Comment on lines
+93
to
+101
| # Ship more, worry about the backend less | ||
|
|
||
| A faster, more available agent is only useful if there is something on the other side of its diffs ready to receive what it builds. Auth, databases, storage, functions, an API layer. The stack that usually eats the time the agent saves. If Codex finishes a feature in 20 minutes and you spend the next 4 hours wiring it into your backend, the gain is gone. | ||
|
|
||
| [Appwrite](/) is an open source backend as a service that includes [Auth](/docs/products/auth), [Databases](/docs/products/databases), [Storage](/docs/products/storage), [Functions](/docs/products/functions), [Messaging](/docs/products/messaging), and [Sites](/docs/products/sites), an open source Vercel alternative for deploying your web app next to your backend. It is available as both managed Cloud and self hosted. Instead of standing up auth, schemas, file pipelines, deploys, and API layers yourself, you point Codex at an Appwrite project and the whole stack is one project. | ||
|
|
||
| The loop is straightforward. Kick off a task from your phone on the way to the office. Codex inspects the repo, asks any clarifying questions, and starts building against an Appwrite backend that already exists. You review the diff at your desk. Pair the mobile anywhere workflow OpenAI just shipped with a backend that does not need to be hand built every time, and the session translates into product, not scaffolding. | ||
|
|
||
| Want to try this loop end to end? [Create a free Appwrite project](https://cloud.appwrite.io/), open Codex on your phone, and ask it to wire up auth and a database against your new project. By the time you sit down at your desk, you have a working backend and a diff to review. |
Contributor
There was a problem hiding this comment.
We should have a section just for our Codex plugin
Contributor
There was a problem hiding this comment.
Just saw
I don't think we should be adding it separately, rather let it replace this section or merge into it
Contributor
There was a problem hiding this comment.
That will allow this section to feel more organic
Contributor
Author
There was a problem hiding this comment.
Fair, made the edit accordingly
Added information about the Appwrite plugin for Codex, including installation instructions and usage examples.
adityaoberai
requested changes
May 21, 2026
Comment on lines
+93
to
+101
| # Ship more, worry about the backend less | ||
|
|
||
| A faster, more available agent is only useful if there is something on the other side of its diffs ready to receive what it builds. Auth, databases, storage, functions, an API layer. The stack that usually eats the time the agent saves. If Codex finishes a feature in 20 minutes and you spend the next 4 hours wiring it into your backend, the gain is gone. | ||
|
|
||
| [Appwrite](/) is an open source backend as a service that includes [Auth](/docs/products/auth), [Databases](/docs/products/databases), [Storage](/docs/products/storage), [Functions](/docs/products/functions), [Messaging](/docs/products/messaging), and [Sites](/docs/products/sites), an open source Vercel alternative for deploying your web app next to your backend. It is available as both managed Cloud and self hosted. Instead of standing up auth, schemas, file pipelines, deploys, and API layers yourself, you point Codex at an Appwrite project and the whole stack is one project. | ||
|
|
||
| The loop is straightforward. Kick off a task from your phone on the way to the office. Codex inspects the repo, asks any clarifying questions, and starts building against an Appwrite backend that already exists. You review the diff at your desk. Pair the mobile anywhere workflow OpenAI just shipped with a backend that does not need to be hand built every time, and the session translates into product, not scaffolding. | ||
|
|
||
| Want to try this loop end to end? [Create a free Appwrite project](https://cloud.appwrite.io/), open Codex on your phone, and ask it to wire up auth and a database against your new project. By the time you sit down at your desk, you have a working backend and a diff to review. |
Contributor
There was a problem hiding this comment.
Just saw
I don't think we should be adding it separately, rather let it replace this section or merge into it
Comment on lines
+93
to
+101
| # Ship more, worry about the backend less | ||
|
|
||
| A faster, more available agent is only useful if there is something on the other side of its diffs ready to receive what it builds. Auth, databases, storage, functions, an API layer. The stack that usually eats the time the agent saves. If Codex finishes a feature in 20 minutes and you spend the next 4 hours wiring it into your backend, the gain is gone. | ||
|
|
||
| [Appwrite](/) is an open source backend as a service that includes [Auth](/docs/products/auth), [Databases](/docs/products/databases), [Storage](/docs/products/storage), [Functions](/docs/products/functions), [Messaging](/docs/products/messaging), and [Sites](/docs/products/sites), an open source Vercel alternative for deploying your web app next to your backend. It is available as both managed Cloud and self hosted. Instead of standing up auth, schemas, file pipelines, deploys, and API layers yourself, you point Codex at an Appwrite project and the whole stack is one project. | ||
|
|
||
| The loop is straightforward. Kick off a task from your phone on the way to the office. Codex inspects the repo, asks any clarifying questions, and starts building against an Appwrite backend that already exists. You review the diff at your desk. Pair the mobile anywhere workflow OpenAI just shipped with a backend that does not need to be hand built every time, and the session translates into product, not scaffolding. | ||
|
|
||
| Want to try this loop end to end? [Create a free Appwrite project](https://cloud.appwrite.io/), open Codex on your phone, and ask it to wire up auth and a database against your new project. By the time you sit down at your desk, you have a working backend and a diff to review. |
Contributor
There was a problem hiding this comment.
That will allow this section to feel more organic
adityaoberai
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Latest blog about Codex